Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Upgrade nwaku image to v0.26.0 #74

Merged
merged 1 commit into from
Mar 12, 2024
Merged

Conversation

NagyZoltanPeter
Copy link
Contributor

... and utilize Waku Rest reference page access to REST API.

v0.26.0 of nwaku is out!

Copy link
Contributor

@gabrielmer gabrielmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much!

Copy link

@SionoiS SionoiS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very useful thanks for it!

Copy link
Contributor

@Ivansete-status Ivansete-status left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for it! Shall we also change the retention policy to "size:10GB", f.e. ?

@NagyZoltanPeter
Copy link
Contributor Author

Thanks for it! Shall we also change the retention policy to "size:10GB", f.e. ?

Well it is a good question. I think most of the volunteers who start playing with it might find it "too expensive" to say I need to provide 10G for such feature, maybe we should start with less and provide some external shell variable to override the default. WDYT?

@Ivansete-status
Copy link
Contributor

Thanks for it! Shall we also change the retention policy to "size:10GB", f.e. ?

Well it is a good question. I think most of the volunteers who start playing with it might find it "too expensive" to say I need to provide 10G for such feature, maybe we should start with less and provide some external shell variable to override the default. WDYT?

Very good point! Go ahead with that approach :) 🙌

@NagyZoltanPeter
Copy link
Contributor Author

Thanks for it! Shall we also change the retention policy to "size:10GB", f.e. ?

Well it is a good question. I think most of the volunteers who start playing with it might find it "too expensive" to say I need to provide 10G for such feature, maybe we should start with less and provide some external shell variable to override the default. WDYT?

Very good point! Go ahead with that approach :) 🙌

Ok, let me add in a separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants